Monitoring Digital Images

ABSTRACT

Digital images are monitored by enabling access to a digital image, receiving a notification associated with the digital image from a first user, and regulating access of the first user to the digital image based on the notification received from the first user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority from U.S.patent application Ser. No. 13/769,203, filed on Feb. 15, 2013, which isa continuation of U.S. patent application Ser. No. 12/838,588, filed onJul. 19, 2010, which issued on Feb. 19, 2013, now U.S. Pat. No.8,380,844, which is a continuation of U.S. patent application Ser. No.11/539,587, filed Oct. 6, 2006, which issued on Aug. 17, 2010, now U.S.Pat. No. 7,779,117, which is a continuation of U.S. patent applicationSer. No. 10/158,180, filed May 31, 2002, which issued on Oct. 10, 2006,now U.S. Pat. No. 7,120,687, which claims priority from U.S. applicationSer. No. 10/007,696, filed Dec. 10, 2001, which issued on Mar. 27, 2007,now U.S. Pat. No. 7,197,513, which claims priority to U.S. provisionalapplication 60/251,834, filed Dec. 8, 2000, all of which are herebyincorporated by reference in their entirety.

TECHNICAL FIELD

The present invention relates generally to an online communicationssystem and more particularly to an online communications system formonitoring digital images.

BACKGROUND

In the client-server network architecture of the Internet and/or Web,electronic documents are stored in computer systems running serverprograms and are accessed by computer systems running client programs.For example, information on the Web is made available by Web servers foraccess by client programs such as Web browsers (e.g., Netscape'sNavigator, Microsoft's Internet Explorer, Java's micro-browser).

Information on the Internet and/or Web may be represented by speciallyformatted text files (e.g., Web pages) written in Hypertext MarkupLanguage (“HTML”) or some other markup language, such as XML, DHTML,and/or VRML. Each text file may be identified by a network address suchas a Universal Resource Locator (“URL”). A typical Web page may includeone or more hyperlinks that refer to the network addresses of other Webpages. Hyperlinks may be displayed as underlined text or graphicalimages that, when clicked, send a request for the associated page. Forexample, when a hyperlink in a home page is selected, a request is sentout by the client to the address specified in the hyperlink, and theassociated Web page is downloaded and displayed, replacing the home pageon the user's screen with the associated Web page.

Browsers and other client programs typically use a communicationsprotocol such as Hypertext Transfer Protocol (“HTTP”) to request pagesfrom Web servers. HTTP is a request/response protocol. Through aconnection established between a client and a server, the client sends arequest to the server, and the server provides a response to the client.

An online service provider (e.g., an Internet service provider (“ISP”))may be used to provide users with access to the Internet and/or WorldWide Web (“Web”). In general, a user relies on an ISP to enablecommunication over the Internet and/or Web. An ISP may offer services inaddition to basic Internet access such as, for example, providing emailand instant messaging services enabling electronic communication,Web-hosting services allowing users to publish homepages, newsgroupservices allowing users to read and post to newsgroups, and imageservices allowing users to view and order digital images of picturesfrom a developed film roll.

SUMMARY

In one general aspect, digital images are monitored by enabling accessto a digital image, receiving a notification associated with the digitalimage from a first user, and regulating access of the first user to thedigital image based on the notification received from the first user.

Implementations may include one or more of the following features. Forexample, access of the first user to the digital image may be regulatedby identifying a storage location associated with the first user, andmodifying metadata associated with the first user. The storage locationmay be identified based upon an application of a hashing code to accountinformation associated with the first user. Metadata to be modifiedincludes metadata associated with the digital image, and modifyingmetadata may include removing metadata corresponding to the digitalimage from one or more tables associated with the first user. Modifyingmetadata may also include removing metadata corresponding to the firstsubscriber from one or more tables associated with the digital image.

In another implementation, access of a second user to the digital imagemay be regulated based on the notification received from the first user.In yet another implementation, access of an owner of the digital imageto the digital image may be regulated. For example, the access of theowner of the digital image may be regulated by identifying a storagelocation associated with the owner and modifying metadata associatedwith the owner. The storage location may be identified based upon anapplication of a hashing code to account information associated with theowner. Modifying metadata may include modifying metadata associated withthe digital image. Modifying metadata may also include removing metadatacorresponding to the first user from one or more tables associated withthe digital image. Moreover, modifying metadata also includes insertingmetadata indicating an investigation status in one or more tablescorresponding to the digital image.

Another implementation includes initiating an investigation of thedigital image based on the notification received from the first user.The investigation may be initiated after receiving a number ofcomplaints from one or more users exceeding a predetermined threshold. Alevel may be assigned to the digital image corresponding to the degreeof offensiveness of the digital image determined by the investigation.

The storage location containing the digital image may be identified. Inone implementation, the storage location maybe identified based uponaccount information associated with the first user. In anotherimplementation, the storage location may be identified based uponaccount information associated with the owner. In yet anotherimplementation, the storage location maybe identified based upon a firstimage identifier associated with a first storage facility and adirectory and a second image identifier comprising a random number.Metadata associated with the stored digital image may be changed toeffect restrictive access to the digital image by the first subscriber.

The digital image may be retrieved. The digital image may be reviewed,and action may be taken based upon the review of the digital image. Forexample, the action may include sending a warning notice to the owner ofthe digital image. The action may also include unsharing the digitalimage to prevent access to the digital image by one or more users, orreplacing the offending digital image with a different digital image.

Other features and advantages will be apparent from the followingdescription, including the drawings, and from the claims.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating aspects of a computer system.

FIG. 2 is a block diagram expansion of aspects of FIG. 1.

FIG. 3 is a block diagram expansion of aspects of FIG. 2

FIG. 4 is a block diagram expansion of aspects of FIG. 2

FIG. 5 is a flowchart of a method that may be implemented by a computersystem such as the computer system illustrated by FIGS. 1-4.

FIG. 6 is a flowchart of another method that may be implemented by acomputer system such as the computer system illustrated by FIGS. 1-4.

DETAILED DESCRIPTION

Computer system users are able to share digital images with each other,and an image service may be provided to facilitate the sharing ofdigital images. Typically, a user will create an online album of digitalimages and then invite one or more other users. to view the onlinealbum. While this feature of the image service allows families andfriends to share life events captured with digital images, it introducesa potential for abuse. For instance, a user may be invited to view adigital image that he or she finds offensive. Typically, this situationarises when a user obtains a list of e-mail addresses through dubiousmeans and mass invites the group of other users to view adult-orientedmaterial.

To protect users, the image service may be configured to monitor digitalimages and receive notifications from users regarding offensive content.In one implementation, a monitoring system is configured to receivenotifications of offending content from users and to take appropriateand automated actions in response to such notifications.

For the sake of brevity in the following description, several elementsin the figures are represented as monolithic entities. However, theseelements each may include numerous interconnected computers andcomponents designed to perform a set of specified operations.

FIG. 1 illustrates an exemplary computer system 100 for implementingtechniques to process digital images. As shown, the computer system 100includes a client system 10 connected through a network 15 to a hostsystem 20. The client system 10 is configured to send requests and thehost system 20 is configured to respond to requests.

In general, the client system 10 and host system 20 each includecomputer systems having hardware and/or software components forcommunicating across the network 15. The client system 10 and hostsystem 20 each may include one or more general-purpose computers (e.g.,personal computers and/or servers), one or more special-purposecomputers (e.g., devices specifically programmed to communicate witheach other), or a combination of one or more general-purpose computersand one or more special-purpose computers. The client system 10 and hostsystem 20 may be structured and arranged to communicate using variouscommunication protocols (e.g., HTTP, WAP) and encapsulation protocols(e.g., UDP) to establish connections (e.g., peer-to-peer) betweennetwork elements and/or to operate within or in concert with one or moreother systems (e.g., the Internet and/or Web).

In one implementation, the client system 10 and the host system 20 eachinclude a device (e.g., client device 12, host device 22) operatingunder the command of a controller (e.g., client controller 14, hostcontroller 24). An example of a device is a general-purpose computercapable of responding to and executing instructions in a defined manner.Other examples include a special-purpose computer, a personal computer(“PC”), a workstation, a server, a laptop, a Web-enabled telephone, aWebenabled personal digital assistant (“PDA”), an interactive televisionset, a set top box (“STB”), video tape recorder (“VTR”), a digital videodisc (“DVD”) player, or any other component, machine, tool, equipment,or some combination thereof capable of responding to and executinginstructions.

An example of a controller is a software application (e.g., operatingsystem, browser application, microbrowser application, serverapplication, proxy application, gateway application, tunnelingapplication, e-mail application, instant messaging client application,online service provider client application, interactive televisionclient application, and/or ISP client application) loaded on a devicecommanding and directing communications enabled by the device. Otherexamples include a computer program, a piece of code, an instruction,another device, or some combination thereof, for independently orcollectively instructing the device to interact and operate as desired.The controller may be embodied permanently or temporarily in any type ofmachine, component, physical or virtual equipment, storage medium, orpropagated signal capable of providing instructions to a device. Inparticular, the controller (e.g., software application and/or computerprogram) may be stored on a storage media or device (e.g., read onlymemory (“ROM”), magnetic diskette, or propagated signal) readable by ageneral or special purpose programmable computer, such that thefunctions described herein are performed if the storage media or deviceis read by a computer system.

The client system 10 is generally located at or on a device, such as,for example, a personal computer, operated or interfaced by a user whorequests or submits information.

The host system 20 may include and/or form part of an informationdelivery network, such as, for example the Internet, the World Wide Web,an online service provider, and/or any other analog or digital wiredand/or wireless network that provides information. Such an informationdelivery network may support a variety of online services includingInternet and/or web access, e-mail, instant messaging, paging, chat,interest group, audio and/or video streaming, and/or directory services.

The network 15 may include one or more delivery systems for directly orindirectly connecting the client system 10 and the host system 20,irrespective of physical separation. Examples of delivery systemsinclude, but are not limited to, a local area network (“LAN”), a widearea network (“WAN”), the Internet, the Web, a telephony network (e.g.,analog, digital, wired, wireless, PSTN, ISDN, or xDSL), a radio network,a television network, a cable network, a satellite network, and/or anyother wired or wireless communications network configured to carry dataEach network may include one or more elements, such as, for example,intermediate nodes, proxy servers, routers, switches, adapters, andwired or wireless data pathways, configured to direct and/or deliverdata.

The network 15 may include one or more delivery systems for directly orindirectly connecting the client system 10 and the host system 20,irrespective of physical separation. Examples of delivery systemsinclude, but are not limited to, a local area network (“LAN”), a widearea network (“WAN”), the Internet, the Web, a telephony network (e.g.,analog, digital, wired, wireless, PSTN, ISDN, or xDSL), a radio network,a television network, a cable network, a satellite network, and/or anyother wired or wireless communications network configured to carry dataEach network may include one or more elements, such as, for example,intermediate nodes, proxy servers, routers, switches, adapters, andwired or wireless data pathways, configured to direct and/or deliverdata.

Referring to FIG. 2, the communications system 200 is an expansion ofthe block diagram of FIG. 1, focusing primarily on one particularimplementation of the host system 20. The host system 20 includes a hostdevice 22 and a host controller 24. The host controller 24 generally iscapable of transmitting instructions to any or all of the elements ofthe host device 22. For example, in one implementation, the hostcontroller 24 includes one or more software applications loaded on thehost device 22. In other implementations, the host controller 24 mayinclude any of several other programs, machines, and devices operatingindependently or collectively to control the host device 22.

The host device 22 includes a login server 210 for enabling access byusers and for routing communications between the client system 10 andother elements of the host device 22. The host device 22 also mayinclude one or more host complexes, such as the depicted InstantMessaging (“IM”) host complex 220 and Online Service Provider (“OSP”)host complex 230. To enable access to these host complexes, the clientsystem 10 includes communication software (not explicitly shown), forexample, an IM client application, an OSP client application, and/or abrowser application. The IM and OSP communication software applicationsare designed to facilitate interactions with the respective servicesand, in particular, may provide access to any or all of the servicesavailable within the respective host complexes. Furthermore, in oneimplementation, the login server 210 may initiate or facilitate one ormore authorization procedures to enable independent or concurrent accessto the IM host complex 220 and the OSP host complex 230.

The IM host complex 220 and the OSP host complex 230 may be connectedthrough one or more gateways (not shown) that perform protocolconversions necessary to enable communications between the IM hostcomplex 220, the OSP host complex 230, and the Internet 30. However, theIM host complex 220 generally is independent of the OSP host complex230, enabling support of instant messaging services irrespective ofnetwork or Internet access. Thus, the IM host complex 220 allows usersto send and receive instant messages, whether or not they have access toany particular ISP. The IM host complex 220 may support associatedservices, such as administrative matters, advertising, directoryservices, chat, and interest groups related to instant messaging. The IMhost complex 220 is capable of enabling any or all of the machineslogged into the IM host complex 220 to communicate with each other. Totransfer data, the IM host complex 220 employs one or more standard orexclusive IM protocols.

Typically, the OSP host complex 230 supports different andnon-instantaneous services, such as e-mail services, discussion groupservices, chat, news services, and Internet access services. Inaddition, the OSP host complex 230 may offer IM services independent ofor based on IM host complex 220. The OSP host complex 230 generally isdesigned with an architecture that enables the machines within the OSPhost complex 230 to communicate with each other and employs certainprotocols (i.e., standards, formats, conventions, rules, and structures)to transfer data. For instance, the OSP host complex 230 ordinarilyemploys one or more OSP protocols and custom dialing or broadbandengines to enable access by selected client applications. The OSP hostcomplex 230 may define one or more specific protocols for each servicebased on a common, underlying proprietary protocol.

The OSP host complex 230 supports a set of services from one or moreservers that communicate with the OSP host complex 230 and that may bephysically located internal or external to the OSP host complex 230. Forpurposes of this discussion, servers external to the OSP host complex230 generally may be viewed as existing on the Internet 30. Serversinternal to the OSP complex 230 may be arranged in one or moreconfigurations. For example, servers may be arranged in centralized orlocalized clusters in order to distribute servers and users within theOSP host complex 230.

In the implementation shown by FIG. 2, the OSP host complex 230 includesa routing processor 232. In general, the routing processor 232 willexamine an address field of a data request, use a mapping table todetermine the appropriate destination for the data request, and directthe data request to the appropriate destination. More specifically, in apacket-based implementation, the client system 10 may generateinformation requests, convert the requests into data packets, sequencethe data packets, perform error checking and other packet-switchingtechniques, and transmit the data packets to the routing processor 232.Upon receiving data packets from the client system 10, the routingprocessor 232 may directly or indirectly route the data packets to aspecified destination within or outside of the OSP host complex 230. Forexample, in the event that a data request from the client system 10 canbe satisfied locally, the routing processor 230 may direct the datarequest to a local server 236. In the event that the data request cannotbe satisfied locally, the routing processor 232 may direct the datarequest externally to the Internet 30 or the IM host complex 220.

The OSP host complex 230 also includes a proxy server 234 for directingdata requests and/or otherwise facilitating communication between theclient system 10 and the Internet 30. The proxy server 234 may includean Internet Protocol (“IP”) tunnel capable of converting data between anOSP protocol and standard Internet protocol to enable the client system10 to communicate with the public Internet 30, if appropriate.

The proxy server 234 also may allow the client system 10 to use standardIPs and formatting to access the OSP host complex 230 and the Internet30. For example, the user may use an OSP TV client application having anembedded browser application installed on the client system 10 togenerate a request in a standard IP format such as HTTP. In apacket-based implementation, data packets may be encapsulated inside astandard Internet tunneling protocol, such as, for example, UserDatagram Protocol (“UDP”), and routed to the proxy server 234. The proxyserver 234 may initiate a tunneling protocol, such as a Layer TwoTunneling Protocol (“L2TP”) tunnel, to establish a point-to-pointprotocol (PPP) session with the client system 10.

The proxy server 234 also may act as a buffer between the client system10 and the Internet 30, and may implement content filtering and timesaving techniques. For example, the proxy server 234 can access parentalcontrols settings established for the client system 10 or contentrequestor and enable requests and for transmission of content from theInternet 30 and other accessible content servers according to theparental control settings accessed. In addition, the proxy server 234may include one or more caches for storing frequently accessedinformation, or may enable access to similar caches stored elsewhere. Ifrequested data is determined to-be stored in the caches, the proxyserver 234 may send the information to the client system 10 from thecaches and avoid the need to access the content source, e.g., theInternet 30.

The OSP host complex 230 further includes a mail system 238, an imagefarm 240, a film handler 242, an account manager 244, and a monitoringsystem 246 in communication with each other as well as the otherelements in the communications system 200.

The mail system 238 is configured to receive, store, retrieve, route,and deliver electronic mail (“e-mail”) messages. In one implementation,the mail system 238 includes a system of folders or mailboxes associatedwith the users of the OSP host complex 230 and a massive storage areafor storing the contents of e-mail messages including attachments to thee-mail messages. When the mail system 238 receives an e-mail messageaddressed to a particular user, the mail system stores the content andattachments of the e-mail message, inserts a link (e.g., href) orpointer corresponding to the storage location into the user's mailbox,and alerts the user of the new mail. The user opens the e-mail messageby logging into the mailbox and selecting an icon including the link tothe stored e-mail message. Similarly, a user may send an e-mail messageby logging into the mailbox, generating an e-mail message, and thenselecting a “send” button that causes the mail system 238 to store andforward the e-mail message to one or more intended recipients.

The image farm 240 is configured to receive, store, retrieve, route,and/or deliver digital images from developed rolls of film. The imagefarm 240 includes a system of storage servers and databases for storingdigital images and metadata describing the digital images. Typically,digital images and metadata are stored in a distributed fashion acrossseveral storage facilities and/or databases. For example, digital imagesmay be stored independently of the submitter and of the original filmroll such that image data for a particular submitter or roll ismaintained over several different storage facilities. More specifically,each of twenty-four pictures from a single roll may be stored atdifferent storage facilities, or one or more may be stored at a singlefacility. Thus, the overall integrity of the image service provided bythe OSP host complex 230 can be preserved even in the event of acatastrophic outage of several storage facilities. In addition,compromises to the security of a single server will not necessarily leadto access of more than one picture in a roll of film or by a particularsubmitter. Metadata describing the image data also may be distributedacross a system of databases such that no one database is responsiblefor a disproportionate amount of metadata. The image farm 240 isdescribed in greater detail below.

The film handler 242 is configured to receive and route digital imagesto the image farm 240 as well as update metadata maintained in the imagefarm 240. In general, upon receiving a collection of digital images, thefilm handler 242 transfers the image data to the image farm 240 forstorage and updates metadata associated with the digital images.Typically, the film handler 242 receives digital images from a user orfrom a third party (e.g., film developer) associated with the user ofthe OSP host complex 230. For example, the film handler 242 may receiveone or a collection of digital images created with a digital camera froma user. The user may upload the digital images using one or moresoftware applications provided by the OSP host complex 230 or thedigital camera manufacturer. Alternatively, the film handler 242 mayreceive a collection of digital images from a film developer thatreceived an undeveloped roll of film from a user, developed the roll offilm, created digital images from the developed roll, and sent thedigital images to the film handler 242.

In one implementation the film handler 242 includes application serverlogic (e.g., Netscape Application Server (NAS) logic or Java Server(KJS) logic) for maintaining a pool of database connections for highperformance accesses into databases in the image farm 240. The filmhandler 242 also may include a hash value-to-database function libraryfor determining where database reads and writes occur within thedatabases. While the film handler 242 is depicted in FIG. 2 as beingexternal to the image farm 240, in another implementation, the filmhandler 242 may reside as an application (e.g., Java applet) runningwithin the image farm 240.

The account manager 244 is configured to maintain an image serviceaccount for the users of the OSP host complex 230. In general, theaccount manager 244 creates new accounts by requesting information fromand inserting submitted account information into account tablesmaintained in the image farm 240. In one implementation the accountmanager 244 includes application server logic (e.g., NetscapeApplication Server (NAS) logic or Java Server (KJS) logic) formaintaining a pool of database connections for high performance accessesinto databases in the image farm 240. The account manager 244 also mayinclude a hash value-to-database function library for determining wheredatabase reads and writes occur within the databases. In general, theaccount manager 244 creates an image service account and populates acertain account table in the image farm 240. The account manager 244also may automatically generate certain account information (i.e.,fields) based on the information submitted from users. In addition, theaccount manager 244 may be configured to authenticate users logging into the image service, deliver path information (e.g., linkinginformation) to users in response to requests for various image servicefeatures, and transmit purging information in response to complaintsreceived from users.

The monitoring system 246 is configured to locate and remove storedimages that violate policies established by administrators of the OSPhost complex 230. In general, the policies regulate the type of contentthat is acceptable for sharing among users. While the OSP host 230provides users with the ability to share digital images with otherusers, the monitoring system 246 is designed to temper that ability inorder to protect users from viewing offensive content. Although themonitoring system 246 may act proactively by filtering submitted digitalimages and deleting digital images that are deemed offensive, themonitoring system 246 typically is configured to receive notificationsof offending content from users and take appropriate actions inresponse. The monitoring system may take different levels of actiondepending upon the nature of the offending content. Such actions mayrange, for example, from blocking the complaining user from reviewingthe offending digital image to deleting the digital image, canceling theoffender's account, and alerting law enforcement authorities. Themonitoring system 246 is described in greater detail below.

The separate illustration and description of host complex items, such asthe routing processor, 232, proxy server 234, local server 236, mailsystem 238, image farm 240, film handler 242, account manager 244, andmonitoring system 246, is not to imply the distinction of hardwareand/or software used to enable those items. Rather one or more of theseitems may be combined.

FIG. 3 is one implementation of the image farm 240 of FIG. 2. As shown,the image farm 240 includes a distribution server 2402 in communicationwith several image farm databases 2404. Each image farm database 2404includes several tables (e.g., film and image tables 2406 and accounttables 2408) for maintaining information associated with receiveddigital images and the users of the OSP host complex 230. In general,the distribution server 2402 is configured to identify storage locationswithin the image farm databases 2404. The distribution server 2402 maycommunicate with and receive information (e.g., image metadata) fromvarious other elements of the OSP host complex 230 of FIG. 2, including,e.g., the mail system 238, the film handler 242, the account manager244, and the monitoring system 246. The distribution server 2402 also isconfigured to insert, update, and/or delete information from identifiedstorage locations. For example, the distribution server 2402 may receivemetadata from the film handler 242, identify a storage location in theimage farm database 2404 based on the metadata, and insert the metadatainto an appropriate table at the identified storage location. Thedistribution server 2402 also may receive metadata from the monitoringsystem 246, identify a Storage location in the image farm database 2404based on the metadata, and delete/replace stored metadata from anappropriate table at the identified storage location.

The image farm 240 further includes an image storage server system 2410having an image storage server 2412, an image write server 2414, animage read server 2416, and an image purge server 2418. In general, theimage write server 2414 is configured to insert image data into theimage storage server 2412, the image read server 2416 is configured toretrieve image data from the image storage server 2412, and the imagepurge server 2418 is configured to delete image data from the imagestorage server 2412.

The image storage server system 2410 may communicate with and respond tovarious elements of FIG. 2, including the client system 10, the filmhandler 242, the account manager 244, and the monitoring system 246.Servers (e.g., image write server 2414, image read server 2416, andimage purge server 2618) of the image storage server system 2410 mayfunction in response to a communication from the client system 10, thefilm handler 242, the account manager 244, and/or the monitoring system246. For example, the image write server 2414 may generate metadata andstore image data in the image storage server 2412 in response to acommunication from the film handler 242. The image read server 2416 mayretrieve image data in response to a communication from a client system10 according to path information provided by the account manager 244.The image purge server 2418 may delete image data in response to acommunication from the monitoring system 246.

In one implementation, each image storage server 2412 may store digitalimages according to the following directory structure:

host:/data/AAA/BB/CC/DD/EE/ID_N.type.

In this pneumonic directory structure, host identifies a particularimage storage server 2412 (root directory) for storing a digital image,data identifies a static directory of the image storage server 2412, AAAis a three hexadecimal character directory identifier denoting a mainstorage directory of the image storage server 2412, BB, CC, DD, and EEare each two hexadecimal character subdirectories in the image storageserver 2412, ID is an encrypted 32 hexadecimal character imageidentifier that provides a file name and contains location information,N is the largest pixel dimension of an image (width or height), and typeidentifies image type (e.g., jpg).

By design, the above directory structure limits the number of files thatcan exist in one subdirectory while still establishing enoughsubdirectories so that the system will be relatively sparse. With thisdirectory structure, for example, an image storage server 2412 may bedesigned with limits of 256 images and 256 subdirectories (designated bytwo hexadecimal digits) within a single tier. The file systems aremounted below the server root directory at the /data/AAA level. Thisensures that the AAA level as well as the host level will be relativelysparse, while the BB, CC, DD and EE levels will be heavily populated. Inone implementation, IDs are varied over the BB and host range quickly.The ID field resides beneath the EE level, since ID is a uniqueidentifier and only one file will have that unique path. The directorystructure is very robust, enabling each file system to store in excessof two billion images, even if only IDs are considered. It should benoted that the specific numerical values provided are exemplary only.

FIG. 4 provides further detail regarding the image farm databases 2404of FIG. 3. As shown, the image farm databases 2404 are separated intomultiple storage space groups referred to as “buckets.” In oneimplementation, the image farm databases 2404 are separated into sixteenrelatively equal-sized buckets (bucket 0-bucket 15). As described above,each image farm database 2404 maintains information associated withreceived digital images and the users of the OSP host complex 230. Thisinformation is received by the image farm databases 2404 and is storedwithin the film and image tables 2406 and account tables 2408 in adistributed fashion. Namely, the information received by the image farmdatabases 2404 is relatively uniformly distributed across more than oneor all buckets. Distributing information across multiple storage spacesareas in this way eliminates the need to scan across multiple databasesfor the most common image service operations offered by the OSP hostcomplex 230.

In one implementation, relatively uniform distribution across allbuckets is accomplished by applying an OSP proprietary hashing code toat least one field in the received information. Application of the OSPproprietary hashing code returns a unique hash value. The hash valuethen is transformed into a bucket number corresponding to one of therelatively equal-sized buckets. The information is routed to theappropriate bucket, each bucket containing sets of film and image tables2406 and account tables 2408 configured to store the receivedinformation in appropriate fields.

Each of the bucketed image farm databases 2404 includes film and imagetables 2406 and account tables 2408. In one implementation, the film andimage tables 2406 include a film reference table 2406 a containingsharing information related to a film, a film table 2406 b fordescribing a collection of images, an image reference table 2406 ccontaining information showing that an image has been used to constructa film, an image table 2406 d for describing a particular image, a filmattributes table (not shown) for storing future or less commonroll/album properties that are not included in the film table, an imageattributes table (not shown) for storing future or less commonproperties that are not included in the image table, a filmidentification counter (not shown) that may be used to generate a uniquefilm identifier without the need for an external server, and an imagecopyright table (not shown) for flagging images that have copyrightinformation bound to them. The account tables 2408 include an accountinformation table 2408 a for storing account information associated witha particular user.

The film reference table 2406 a may include information such as: filmidentifiers, reference owner, shared by name, buddy name, film referenceidentifier, film type, number of images, title, share type, accesscontrol, modification date, first viewed date, and view flag. In oneimplementation, fields for the film identifiers, reference owner, sharedby name, buddy name, and film reference identifier are designated asprimary keys for sorting and searching the film reference table as wellas for establishing relationships among the film reference table andother tables and/or databases.

The film table 2406 b may include information such as: film identifiers,owner name, film type, number of images, creation status, creation date,modification date, expiration date, external film identifier, owner key,reference counter, access control, purge flags, title, description,background pattern, layout, or other attributes. In one implementation,fields for the film identifiers are designated as primary keys forsorting the film table as well as for establishing relationships amongthe film table and other tables and/or databases.

The image reference table 2406 c may include information such as: filmidentifiers, image identifiers, image version, image counter, sequencenumber, image hash value, caption, creation date, modification date,frame type, image type, resolution, maximum width, maximum height,access control, purge flags, and branding identifier. In oneimplementation, fields for the film identifiers, image identifiers,image version, image counter and the sequence number are designated asprimary keys for sorting the image reference table as well as forestablishing relationships among the image reference table and othertables and/or databases.

The image table 2406 d may include information such as: imageidentifiers, image version, original owner, image type, resolution,maximum width, maximum height, access control, purge flags, brandingidentifier, creation status, creation date, modification date, referencecounter, external film identifier, external user name, externalfilename, source identifier, rotation angle, archived flag, copyrightflag, and attribute flag. In one implementation, fields for the imageidentifiers and image version are designated as primary keys for sortingthe image table as well as for establishing relationships among theimage table and other tables and/or databases.

The film attributes table may include information such as: filmidentifiers, image version, attribute type, and attribute string. In oneimplementation, fields for the film identifiers, image version, andattribute type are designated as primary keys for sorting and searchingthe film attributes table as well as for establishing relationshipsamong the film attributes table and other tables and/or databases.

The image attributes table may include information such as: imageidentifiers, image version, attribute type and attribute string. In oneimplementation, fields for the image identifiers, image version andattribute type are designated as primary keys for sorting the imageattributes table as well as for establishing relationships among theimage attributes table and other tables and/or databases.

The film identification counter may include information such as: hashvalue and identifier counter. In one implementation, the field for thehash value is designated as the primary key for sorting the filmidentification table as well as for establishing relationships among thefilm identification table and other tables and/or databases.

The image copyright table may include information such as: imageidentifiers, image version, line number, and copyright information. Inone implementation, fields for the image identifiers, image version andline number are designated as primary keys for sorting the imagecopyright table as well as for establishing relationships among theimage copyright table and other tables and/or databases.

The account information table 2408 a may include information such as:account name (e.g., screen name), a unique identifier (e.g., hash value)associated with the account name, image storage space used, imagestorage space available, account type, billing cycle, account creationdate, modification date, account preferences, number of rolls, number ofalbums, number of shared accounts (e.g., buddies), notification flagsconcerning offensive content, pertinent dates (e.g., last login, lastroll received, last image uploaded, last album shared, last mailreceived, last mail sent, welcome kit received), and/or otherinformation. In one implementation the account name is designated as theprimary key for sorting the account information table as well as forestablishing relationships among the account information table and othertables and/or databases.

Referring to FIG. 5, a procedure 500 for monitoring and providing accessto digital images may be implemented by a computer system 100 such as,e.g., that illustrated and described with respect to FIGS. 1-4. Thatsaid, the procedure 500 may be implemented by any suitable type ofhardware (e.g., device, computer, computer system, equipment,component); software (e.g., program, application, instructions, code);storage medium (e.g., disk, external memory, internal memory, propagatedsignal); or combination thereof.

Initially, a new image service account is created (step 505). Ingeneral, the host system 20 creates image service account for users. Inone implementation, the host system 20 includes an OSP host complex 230that receives subscriptions from users and offers image services as partof a package of online service available to users. Typically, the hostsystem 20 (e.g., account manager 244) automatically creates an imageservices account for a user at the time of OSP subscription. In otherimplementations, the host system 20 may offer image services tocustomers of a film-processing partner regardless of the customers' ISP.In such implementations; the host system 20 (e.g., account manager 244)may prompt the user to enter account information through a userinterface or it may obtain information electronically from storage atthe host 20 or another accessible system.

Creating an image service account 505 may involve automaticallygenerating certain account information (i.e., fields). For example,typical account information may include but is not limited to, accountname (e.g., screen name), a unique identifier (e.g., hash value)associated with the account name, image storage space used, imagestorage space available, account type, billing cycle, account creationdate, modification date, account preferences, number of rolls, number ofalbums, number of shared accounts (e.g., buddies), notification flagsconcerning offensive content, pertinent dates (e.g., last login, lastroll received, last image uploaded, last album shared, last mailreceived, last mail sent, welcome kit received), and/or other personalinformation (e.g., mailing address, phone number, instant messagecontacts, e-mail contacts). In general, the host system 20 (e.g.,account manager 244) may be configured to automatically detect andupdate information to populate these fields with little or no inputrequired by the user.

Creating an image service account 505 also may involve storing and/oraccessing account information in a distributed fashion. In general, theaccount information is maintained on the host system 20 in massivestorage facilities. In one implementation, the host system 20 includesan image farm 240 and an account manager 244 for populating the imagefarm 240. The image farm 240 includes a plurality of image farmdatabases 2404 for storing account information in account tables 2408.Each of the image farm databases 2404 may be assigned to one of aplurality of storage space groups (e.g., buckets). Account informationis relatively uniformly distributed to a particular storage space group,i.e. bucket, and stored in an appropriate table (e.g., accountinformation table 2408 a) in one of the bucketed image farm databases2404.

Distributing the account information to an appropriate storage spacegroup may include determining a unique hash value by encoding theaccount information. For example, the account name (e.g., screen name)associated with a user may be encoded using a proprietary OSP hashingcode. In one implementation, the host system 20 (e.g., account manager244) applies a hashing code that involves multiplying the individualASCII values of the characters in the screen name by certain primenumbers, summing them, and returning a value modulo 64K (i.e., a 16-bitunsigned integer value between 0-65535). The returned hash values aremapped in round-robin fashion to the storage space groups, i.e.,buckets, according to Table 1.

TABLE 1 Hash Value Bucket 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 1011 11 12 12 13 13 14 14 15 15 16 0 17 1

At any time after creating the image service account (step 505), thehost system 20 (e.g., account manager 244) may update and/or delete theimage service account. In general, the user may actively request thehost system 20 to update or cancel an image service account by loggingin and requesting an update or cancellation. The host system 20 also maydelete a user's account due to inactivity. For example, the host system20 may remove an image service account that has been idle if a user hasnot developed a roll within the last X (e.g., 6) months, uploaded animage within the last Y months, shared an image (e.g., by e-mail or bysharing an album) within the last Z months, or logged in the imageservice feature within the last ZZ months, where X, Y, Z, and ZZ arethreshold values of time which may be the same or which may differ fromone another. Of course, the timing on these activities should beflexible to allow business to adjust as market conditions demand. Inaddition, the host system 20 may delete a user's account due to a policyviolation. For example, sharing inappropriate digital images may resultin cancellation or regulation of a user's image service account, asdiscussed in greater detail below.

Following the creation of an image service account (step 505), one ormore digital images associated with a user are received (step 510). Ingeneral, a host system 20 receives digital images associated with auser. To this end, the host system 20 may include a film handler 242configured to receive digital images from a user or from a third party(e.g., film developer) associated with the user. For example, the filmhandler 242 may receive one or a collection of digital images from auser or from a third party (e.g., film developer). For images receivedfrom a third party, each of the digital images may have a preset maximumresolution (e.g., 768.times.512 pixels) for incoming rolls. Foruser-uploaded images, the size of the digital images may be variablewith no preset maximum resolution.

After one or more digital images are received (step 510), a firststorage facility for storing a digital image is identified (step 515)through selection or through access to a previous selection. In general,the host system 20 identifies a first storage facility for storing adigital image. In one implementation, the host system 20 includes animage storage server system 2410 having a plurality of image storageservers 2412 configured to store digital images. The host system 20further includes a film handler 242 that identifies one of the pluralityof image storage servers 2412 as being available to store a digitalimage. For example, the film handler 242 may access a configuration filethat contains a complete list of image storage servers 2412 and selectsparticular image storage servers 2414 in round-robin fashion. Afterselecting a particular image storage server 2412, the film handler 242may communicate with the image write server 2414 and confirm that theimage storage server 2412 is capable of storing the digital image.

After the first storage facility has been identified (step 515), adirectory within the first storage facility is identified for storing adigital image (step 520). In general, the host system 20 identifies adirectory in the first storage facility. In one implementation, the hostsystem 20 includes a plurality of image storage servers 2412, each imagestorage server 2412 having a directory structure for storing digitalimages. Typically, the directory structure for an image storage server2412 will include several tiers identifying the storage facility, adirectory, and several subdirectories. The host system 20 may include afilm handler 242 that identifies one of the plurality of directorieswithin a particular image storage server 2412 as being available tostore a digital image. For example, the film handler 242 may access aconfiguration file that contains a complete list of first tierdirectories associated with each image storage server 2412. The filmhandler 242 may select particular first tier directories in the imagestorage server 2412 using load balancing algorithms and techniques, suchas the well-known round-robin approach. After selecting a particularfirst tier directory, the film handler 242 confirm that the particularimage storage server 2412 is capable of storing the digital image withinthe particular first tier directory and communicate this information tothe image write server 2414.

After a particular directory within the storage facility has beenidentified (step 520), a first image identifier is generated (step 525).In general, the host system 20 generates a first image identifierassociated with the identified storage facility and directory. In oneimplementation, the host system 20 includes an image write server 2414that generates a first image identifier corresponding to the identifiedstorage facility and the identified directory. One example of a firstimage identifier is an 8 hexadecimal (32 bit) character string in whichthe first three hexadecimal characters correspond to the storagefacility, the next three hexadecimal characters correspond to thedirectory, and the last two hexadecimal characters correspond to anencryption method. Typically, the groups of hexadecimal characterscorresponding to the storage facility, directory, and encryption arecoded. To illustrate, an example of a first image identifier(image_id_p1) is FEDCBA98. In this illustration, the characters FEDcorrespond to a particular storage facility, for example, the imagestorage server 2412 named ygppics-dO1.blue.isp.com. The characters CBAcorrespond to a directory within the particular storage facility, forexample, the main storage directory 010. And, the characters 98correspond to an encryption method, for example, the MD5 algorithm orDEC algorithm.

Next, a second image identifier is generated (step 530). In general, thehost system 20 generates a second image identifier for determiningparticular subdirectories of the identified storage facility. In oneimplementation, the host system 20 includes an image write server 2414that generates a second image identifier using a random numbergenerator. One example of a second image identifier is arandomly-generated 8 hexadecimal (32 bit) character string. Toillustrate, an example of a second image identifier (image_id_p2) is76543210. Typically, the image write server 2414 will generate randomnumbers.

Then, a unique hash value is generated by encrypting the first andsecond image identifiers (step 535). In general, the host system 20encrypts the first and second image identifiers and returns a hashvalue. In one implementation, the host system 20 includes an image writeserver 2414 that encrypts the first and second image identifiersaccording to a selected encryption method (e.g., MD5, DEC). One exampleof an encryption method involves applying the MD5 algorithm to the firstand second image identifiers represented as a single character string(e.g., a single 16 hexadecimal character string). To illustrateaccording to the above example, the first image identifier (image id p1)and the second image identifier (image_id_p2) can be represented as the16 hexadecimal character string, e.g., FEDCBA9876543210. A unique hashvalue is returned when the MD5 algorithm is applied to this characterstring.

In general, encrypting the first and second image identifiers returns anexpanded hash value having more characters than the first and secondimage identifiers. In one implementation, the first and second imageidentifiers each include 8 hexadecimal characters and the retuned hashvalue is a unique 32 hexadecimal character string value. To illustrate,assume that a trivial encryption method involves simply inserting randomcharacters into a 16 hexadecimal characters string (image_id_p1image_id_p2) to create a 32 hexadecimal character string. In such ascase, the result of encrypting the first image identifier (image_id_p1)and the second image identifier (image_id_p2) could be the unique imageidentifier (ID): F1E2D3C4B5A69788796A5B4C3D2E1FO. Of course, in practiceimplementations, more elaborate hashing algorithms, such as the MD5algorithm and/or the DES algorithm, may be utilized so that theresulting hash value gives no clear indication of the type of encryptionalgorithm being employed, or more simplistic security protocols orhashing algorithms may be applied to simplify the process or procedure.

Next, a storage path is identified using the first and second imageidentifiers and the unique hash value (step 540). In general, the hostsystem 20 identifies a storage path for the digital image using thefirst and second image identifiers and the unique hash value.

As described above, each storage server 2412 may store digital imagesaccording to the following directory structure:

host:/data/AAA/BB/CC/DD/EE/ID_N.type

In this pneumonic directory structure, host identifies a particularimage storage server 2412 (root directory) for storing a digital image,data identifies a static directory of the image storage server 2412, AAAis a three character directory identifier denoting a main storagedirectory of the image storage server 2412, BB, CC, DD, and EE are eachtwo character subdirectories in the image storage server 2412, ID is anencrypted character image identifier that provides a file name andcontains location information, N is the largest pixel dimension of animage (width or height), and type identifies image type (e.g., jpg).

Identifying the storage path may include extracting storage pathinformation from the first and second image identifiers, for example,using an image write server 2414 such as that shown by FIG. 3. In oneexample, the first image identifier (image_id_p1) is FEDCBA98 and thesecond image identifier is 76543210. These characters may represent anencoded path (e.g., href) of a storage location in the image storageserver 2412. The host system 20 (e.g., image write server 2414) mayextract path information from the first and second image identifiers asfollows: FED=host, CBA=AAA, 98=encryption code (encryption used toobtain the hash value), 76=BB, 54=CC, 32=DD, and 1O=EE.

Identifying the storage path may involve translating the extracted pathinformation using a decoder (e.g., a look up table). Again using theexample from above in which the first image identifier is FEDCBA98 andthe second image identifier is 76543210, the decoder may translate thehost characters FED into the server name ygppics-dO 1. blue.isp.com, theAAA characters CBA into the main directory 101, the BB characters 76into the first subdirectory 05, the CC characters 54 into the seconddirectory 72, the DD characters 32 into the third subdirectory FA, andthe EE characters 10 into the fourth subdirectory CB.

Identifying the storage path further may include using the unique hashvalue as a filename. As described above, encrypting the first and secondimage values returns a unique filename. This unique hash value may beused as a unique image identifier (ID) that defines a unique file nameand location for the image data. In one example, assuming the largestpixel value is 96 and the digital image is jpg type, the resulting path(href) in this case would be: http://ygppics-dO1.blue.aol.com/data/O10/05/72/F A/CB/hashvalue 96jpg.

From the above, it is evident that the determination of a storage pathmay be made independent of typical image identifiers (e.g., accountname, film roll identifier, date received). It follows, therefore, thatrelated digital images (e.g., same account name, same film rollidentifier, same date received) may have unrelated storage paths. Forexample, digital images from the same roll of film generally will havestorage paths corresponding to different image storage servers 2412,different directories, and different subdirectories. As such, thefailure of one storage facility should have reduced impact on theservice of any particular user. Furthermore, in the unlikely event thatthe storage location of a particular image is obtained or determinedwithout authorization (e.g., hacked), the decoded location of one imagewill give no indication of the storage location of any other relatedimages. Consequently, the overall security of the image service isimproved.

After the storage path is identified (step 540), the digital image isstored at the identified storage path (step 545). In general, the hostsystem 20 stores a digital image at the identified storage path. In oneimplementation, the host system 20 includes an image write server 2414that receives a digital image from a film handler 242 and stores thedigital image in a particular image storage server 2412 at theidentified storage path. Where the storage location is derived from aunique hash value, the storage location will be unique to thatparticular digital image.

Storing the digital image may include generating and storing lowerresolution thumbnails. In general, the host system 20 generates thelower resolution thumbnails. In one implementation, the host system 20includes an image write server 2414 that uses a thumbnail function thatcreates thumbnails by ripping lower resolution images directly from adigital image in the directory in which it was stored. The thumbnailfunction may rip and return a 96.times.64 pixel thumbnail or160.times.107 pixel thumbnail, for example. The thumbnails may be givennames based upon the passed in ID and the resolution. Therefore, thelower resolution thumbnails may be stored in the exact same path as thepath of the original.

After the digital image has been stored (step 545), a second and perhapsdifferent storage facility may optionally be identified for storingmetadata describing the digital image (step 550). In one implementation,the host system 20 includes a film handler 242 configured to identify anappropriate image farm database 2404 separate from the image storageserver system 2410. Identifying an appropriate storage space may includedetermining a storage space group containing the appropriate image farmdatabase 2404 from account information associated with the storeddigital image. For example, the account name (e.g., screen name)associated with a user may be encoded using a proprietary OSP hashingcode. In one implementation, the film handler 242 applies the sameproprietary hashing code to the user's screen name as described aboveand is mapped by the distribution server 2402 to the appropriate storagespace group, i.e., bucket, containing the image farm database 2404.

Then, metadata describing a digital image is stored in the secondstorage facility (step 555). In general, the host system 20 stores themetadata describing a digital image. In one implementation, the hostsystem 20 includes bucketed image farm databases 2404 including film andimage tables 2406 and account tables 2408 for storing metadata. Theimage farm databases 2404 and tables may be separate from the imagestorage server system 2410, and generally contain metadata describingand pointing to the digital images stored in the image storage serversystem.

Storing metadata may include storing the first and second imageidentifiers in appropriate film and image tables 2406 (e.g., filmreference table 2406 a, film table 2406 b, image reference table 2406 c,image table 2406 d). As described above, the stored first and secondimage identifiers may be used to identify a unique filename and storagelocation of a digital image stored in the image storage server system2410. Storing metadata also may include automatically creating newrecords, generating certain metadata (e.g., unique film identifier,copyright attribute), and storing the metadata in appropriate film andimage tables 2406. For example, the film handler 242 or a storedprocedure in the film and image tables 2406 may be used to generate aunique film identifier. Storing metadata also may include updatingaccount information stored in account tables 2408. For example, when anew digital image is stored, the film handler 242 may update counters inthe account table 2408 a of a particular user for number of rolls ornumber of albums.

Finally, access to digital images and metadata describing the digitalimages is provided (step 560). In general, the host system 20 providesaccess to digital images and metadata to users and/or other elementswithin the host system 20, such as the account manager 244 and themonitoring system 246, for example. In one implementation, the imagefarm databases 2404 communicate with and providing information (e.g.,path information) to various elements of the OSP host complex 230 ofFIG. 2 including the account manager 244.

Providing access to digital images and metadata describing the digitalimages may include allowing users to view one or more digital images. Ingeneral, the film and image tables 2406 are searchable by variouscriteria (e.g., primary keys) including screen name. For example, bypassing a user's screen name to the film and image tables 2406, theaccount manager 244 can retrieve image records and/or film recordsassociated with the user's account. Typically, the retrieved recordswill include image identifiers referencing one or more stored digitalimages. The account manager 244 can use the image identifiers (e.g.,image_id_p1 and image_id_p2) to determine the storage path of aparticular digital image stored in a particular image storage server2412 within the image storage server system 2410, as described above. Bynavigating to the appropriate storage path in the image storage serversystem 2410, the account manager 244 can retrieve and display aparticular digital image or set of images to a user.

Providing access to digital images and metadata also may includeallowing users to list and view all rolls for a screen name passed as asearch parameter, to list and view all albums for a screen name passedas a search parameter, to list and view all buddy albums for the screenname passed as a parameter, and/or to list all images for a filmidentifier passed as a parameter. After listing and viewing certaindigital images, rolls, and albums, a user may edit and/or delete any orall of the digital images, rolls, and albums.

Providing access to digital images and metadata also may includeallowing users to share a roll or album. In general, the host system 20allows users to share digital images. In one particular implementation,the account manager 244 shares a digital image by taking film identifierand buddy screen name as arguments, locating a film reference table 2406a in the owner's storage space group (e.g., bucket), creating a newrecord in the owner's film reference table, accessing a film referencetable 2406 a in the buddy's storage space group (e.g., bucket), creatinga record in the buddy's film reference table, and incrementing thenumber of buddies field in the account information table 2408 a in thebuddy's storage space group.

Referring to FIG. 6, a procedure 600 for monitoring and providing accessto digital images may be implemented by a computer system 100 such as,e.g., that illustrated and described with respect to with FIGS. 1-4.That said, the procedure 600 may be implemented by any suitable type ofhardware (e.g., device, computer, computer system, equipment,component); software (e.g., program, application, instructions, code);storage medium (e.g., disk, external memory, internal memory, propagatedsignal); or combination thereof.

As described above, users are able to share digital images with eachother. Typically, an owner will create an online album of digital imagesand then invite one or more other users to view the online album. Aninvitation may be extended to the one or more other users by an e-mailmessage. For example, the owner may assemble a list of invited usersthrough the use of an “invite” feature or otherwise. Elements of thehost system 20 (e.g., mail system 238, account manager 244) may reactactively to the owner's invitation by sending access information (e.g.,storage path/link and password via email) to each of the invited users,or they may react passively by merely enabling invitees for futureaccess based on and in response to requests for such access.

While this feature of the image service allows families and friends toshare life events captured with digital images, it introduces apotential for abuse. For instance, a user may be invited to view adigital image that he or she finds offensive. Typically, this situationarises when an owner obtains a list of e-mail addresses through dubiousmeans and mass invites the group to view adult-oriented material.

To protect users, the host system 20 is configured to receivenotifications from users regarding offensive content. In oneimplementation, the host system 20 includes a monitoring system 246configured to receive notifications of offending content from users andto take appropriate and automated and/or semi-automated actions inresponse to such notifications.

Initially, a notification regarding offensive content is received (step605). In general the host system 20 enables or communicates with a userinterface allowing users transmit notifications. For example, sharedalbums may include a “notify” button that allows an invited user toobject to one or more digital images. In one implementation, when a userclicks the notify button, an e-mail is sent to the monitoring system246; however, other means of communicating notifications are clearlycontemplated. The notification may allow a user to identify a specificoffending image or may allow a user to identify a group of images, suchas an album or film roll containing one or more offensive digitalimages. The user may also be given an opportunity to comment on theimage and provide an explanation of why the image is offensive to theuser.

Next, an investigation report is generated based upon the notification(step 610). In general, the host system 20 generates the investigationreport in an automated fashion. In one implementation, the host system20 includes a monitoring system 246 configured to compile investigationreports in response to notifications from users. Generating aninvestigation report may involve compiling information regarding theoffending digital image or group of images containing one or moreoffending images. Some information may be supplied by the complaininguser(s) and some information may be automatically generated by themonitoring system 246. Different categories or levels indicating thedegree of the image offensiveness/unacceptability may be assigned to theimage, and the action taken may be based upon the assigned level. Forexample, stored images may be scanned periodically for an indicationthat the image has been assigned a certain level, and appropriate actionfor the assigned level may be taken.

The investigation report information may include: the photo ID and thealbum ID of the picture album, the member-created picture album name andthe name, if any, of the individual photos, the screen name of thepicture album owner/creator, an indicator if the album owner is a memberof the OSP or another type of member, the country code of the picturealbum owner, the date and time the picture album was created/edited, thefile size of the reported photo ID for the low resolution image size,the date and time that the report was sent to the image monitoringsystem 246, the screen name of the member reporting the picture album,client information (e.g., platform, client version) of the memberreporting the album, the violation category/level of the offendingimage, comments from the complaining user, and the list of sharedmembers for the reported picture album.

Immediately, or within a relatively short period of time (e.g., 5minutes), after the notification is received, a storage locationassociated with the complaining user is identified (step 615). Ingeneral, the host system 20 identifies an appropriate database (e.g.,image farm database 2404) containing metadata associated with thecomplaining user. Identifying the appropriate database may includedetermining a storage space group containing the appropriate image farmdatabase 2404 from account information associated with the complaininguser. For example, the account name (e.g., screen name) associated withthe complaining user may be encoded using a proprietary OSP hashingcode. In one implementation, the monitoring system 246 applies the sameproprietary hashing code to the user's screen name, as described above,and is mapped by the distribution server 2402 to the appropriate storagespace group, i.e., bucket, containing the image farm database 2404.

After the storage location is identified (step 615), metadata associatedwith the complaining user is modified to block the complaining user fromreviewing the offending image (step 620). In general, the host system 20modifies metadata associated with the complaining user and metadataassociated with the offending digital image. In one implementation, themonitoring system 246 finds a film reference table 2406 a correspondingto the offending digital image in complaining member's bucket. Themonitoring system 246 invokes an unsharing procedure that identifies thecomplaining user's screen name and film identifier corresponding to theoffending digital image as parameters and searches film and image tables2406 and account tables 2408 in the complaining user's bucket. Themonitoring system 246 removes metadata corresponding to the offendingdigital image from tables (e.g., account information table 2406 a)associated with the complaining user and removes metadata correspondingto the complaining user from tables (e.g., film reference table 2406 a)associated with the offending digital image. Alternatively, rather thanmerely removing metadata, the monitoring system 246 may add metadata topositively block the content. Also, metadata may be locked to preventthe owner from making changes to the content.

In yet another implementation, the offending image may be replaced witha nonoffensive image, such as a grayed out or blank image. The offendingimage may be stored in a different location pending review of the image.Typically, the offending image would be stored in a location that is notaccessible by users of the computer system, such as an offline storagelocation while it is being reviewed. If the image is found to benonoffensive after completion of the review, the image may be restoredto its original location. In this fashion, database integrity may bemaintained, yet any existing link on the computer system pointing to thepotentially offensive image will lead to the display of a substitutenon-offensive image. Therefore, it is not necessary to seek out andchange links pointing to the offensive image because it will not resultin a user viewing potentially offensive content. In anotherimplementation, action would be taken only after a final review of theimage is complete.

A storage location associated with the owner of the offending digitalimage also is identified (step 625). In general, the host system 20identifies an appropriate database (e.g., image farm database 2404)containing metadata associated with the owner of the offending digitalimage. Identifying the appropriate database may include determining anaccount name (e.g., screen name) associated with the owner of theoffending digital image. The owner's screen name may be obtained fromthe film reference table 2406 a in the complaining user's bucket, forexample. Identifying the appropriate database also may includedetermining a storage space group containing the appropriate image farmdatabase 2404 from account information associated with the complaininguser. For example, the account name (e.g., screen name) associated withthe offending digital image may be encoded using a proprietary OSPhashing code. In one implementation, the monitoring system 246 appliesthe same proprietary hashing code to the owner's screen name asdescribed above and is mapped by the distribution server 2402 to theappropriate storage space group, i.e., bucket, containing the image farmdatabase 2404.

After the storage location associated with the owner of the offendingdigital image is identified (step 625), metadata associated with theowner is modified to block the owner from sharing the digital image withthe user (step 630). In general, the host system 20 modifies metadataassociated with the owner and metadata associated with the offendingdigital image. In one implementation, the monitoring system 246 finds afilm reference table 2406 a corresponding to the offending digital imagein the owner's bucket. The monitoring system 246 invokes an unsharingprocedure that takes the owner's screen name and film identifiercorresponding to the offending digital image as parameters and searchesfilm and image tables 2406 and account tables 2408 in the owner'sbucket. The monitoring system 246 then removes metadata corresponding tothe complaining user from tables (e.g., film reference table 2406 a)associated with the offending digital image and may insert metadata(e.g., purge flag) into tables (e.g., film reference table 2406 a,account information table 2408 a) indicating that the offending digitalimage is under investigation. At this stage of the procedure 600, thecomplaining user can no longer access the offending digital image.However, reporting a digital image or album may have no effect on theability of other users on the roster of a shared album to view thedigital image or album until after an administrative review iscompleted. However, metadata may optionally be locked to prevent theowner from making changes to the content.

In yet another implementation, the offending image may be replaced witha nonoffensive image, such as a grayed out or blank image, as describedabove.

Next, a separate storage location containing the digital image isidentified (step 635). In general, the host system 20 identifies thestorage location of digital images. In general, the film and imagetables 2406 are searchable by various criteria (e.g., primary keys)including screen name. For example, by passing a complaining user'sand/or owner's screen name to the film and image tables 2406, themonitoring system 246 can retrieve image records and/or film recordsassociated with the offending digital image. Typically, the retrievedrecords will include image identifiers referencing one or more storeddigital images. The monitoring system 246 can use the image identifiers(e.g., image_id_p1 and image_id_p2) to determine the storage path of aparticular digital image stored in a particular image storage server2412 within the image storage server system 2410.

Then, the offending digital image is accessed or otherwise retrieved(step 640). In general, the host system 20 retrieves the offendingdigital images. In one implementation, the host system 20 includes amonitoring system 246 configured to navigate to the appropriate storagepath in the image storage server system 2410.

Next, the offending digital image is reviewed for compliance with theterms of the image service (step 645). In general, the host system 20displays the offending digital image for review. In one implementation,the monitoring system 246 displays a particular offending digital imageto an OSP administrator for review. Typically, the terms of service(e.g., policies) are established by administrators of the OSP hostcomplex 230 and are used to regulate the type of content that isacceptable for sharing among users. In one implementation, the OSPadministrator conducting the review may be a governmental or a thirdparty regulator.

Reviewing a digital image may involve analyzing an investigation reportassociated with the offending digital image. In general, aninvestigation report associated with an offending digital image isstored in a database queue to await action by an OSP administrator.Typically, several OSP administrators will be available to conductreviews. Investigation reports are routed to an appropriate OSPadministrator based on the country code of the owner of the digitalimage.

Reviewing a digital image may involve classifying an investigationreport. The classification may indicate a level corresponding to thedegree of offensiveness/unacceptability of the digital image. Ingeneral, the investigation reports may be categorized according to thereported type of violation and review status. For example, all newreports may be classified as a “general” violation. As reports arereviewed, depending on the content of the page, the report may bedesignated as “acceptable” or “unacceptable.” In addition, a report maydesignate the complaint as relating to a non-garden variety “NOV”violation requiring further review. Further, the OSP administratorreviewing NOV reports may mark reports as pending legal review “PLR” inextreme cases. In general, the OSP administrators may include differentspecialists (e.g., legal personnel) for reviewing different categoriesof violations.

Finally, appropriate action is taken based on conclusions drawn fromreview of the digital image (step 650). In general, the host system 20takes appropriate action based on the review of the digital image by theOSP administrator. In one implementation, the host system 20 includes amonitoring system 246 configured to take different levels of actiondepending upon the nature of the offending content. Such actions mayrange, for example, from blocking the complaining user from reviewingthe offending digital image to deleting the digital image, canceling theoffender's account, and alerting law enforcement authorities. In oneimplementation, the offending image may be replaced with a non-offensiveimage, such as a grayed out or blank image, as described above.

If after reviewing the digital image, the OSP administrator determinesthat there is no violation, the OSP administrator will indicate that thedigital image is “acceptable.” While the complaining user will have nofurther access to the particular image, other users sharing the digitalimage will be unaffected by the complaint. In another implementation, ifthe image had been replaced with a grayed out or other non-offensiveimage, the original image may be restored once the review is completeand the image deemed acceptable.

If the digital image is deemed to be in violation of the terms ofservice or other regulatory requirement, the OSP administrator indicatesthat the digital image is “unacceptable.” In this case, the monitoringsystem 246 may take action with respect to the image itself or theowner. For instance, a warning e-mail may be sent to the owner of theunacceptable digital image, and the violation may be reported ordocumented in the owner's account history. Alternatively, the monitoringsystem 246 may simply unshare the digital image. This function willallow the owner to still have access to their digital images, but nolonger allow the owner to share images or albums with a particular useror users, particular categories of users, or all other users. Dependingon the severity of the violation, the monitoring system 246 also maydelete the digital image and metadata describing the digital image fromall tables and/or terminate the owner's account. In anotherimplementation, the offending image may be replaced with a non-offensiveimage, such as a grayed out or blank image, as described above.

In cases where the content of the digital image warrants further review,the OSP administrator may forward the digital image and its associatedreport to a NOV specialist. The NOV specialist may make a finaldetermination as to whether the digital image is acceptable orunacceptable.

In extreme cases, where the content of the digital image may be illegal,the OSP administrator may forward the digital image and its associatedreport to legal or regulatory personnel, within the OSP organization orotherwise. The monitoring system 246 may block the violator's entirepicture album from being viewed by anyone except OSP administrators andlegal personnel. The legal review specialist may make a finaldetermination as to whether the digital image is acceptable orunacceptable. In some cases, the legal specialist may inform or beaffiliated with law enforcement.

A peremptory, automated investigation or review of an image may bepossible. Also, the action taken in response to a notification of anoffending image may be fully automated or partially automated. Forexample, a human reviewer may manually investigate the image and assignan indication of whether the image is acceptable or unacceptable, andmay also assign a level corresponding to the unacceptability of theimage. In another implementation, the review may be conducted in a fullyautomated manner, using techniques well known in the art. In yet anotherimplementation, an investigation of an image may be undertaken onlyafter reviewing a threshold number of complaints from one or more users.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made and that otherimplementations are within the scope of the following claims. Forexample, if a more elaborate method of preventing unauthorized usersfrom making simple, incremental changes to a known image path (“walkingthe href’) to find other image paths is needed, an encryption algorithmcan be applied to the first and second image identifiers.

1. A method of monitoring digital images, comprising: receiving a useridentity from a user; enabling the user to access a digital image whilethe user operates under the user identity; receiving a notificationassociated with the digital image from the user while the user operatesunder the user identity, wherein the notification indicates that thedigital image is inappropriate; initiating, an investigation of thedigital image based on the notification received from the user; andperforming an action in response to the investigation that affects thedigital image.
 2. The method of claim 1 wherein the action performed isto block the user identity from accessing the digital image.
 3. Themethod of claim 1 wherein the digital image is associated with an owneraccount and the action performed is blocking the owner account.
 4. Themethod of claim 3 wherein the action performed is to block all digitalimages associated with the owner account.
 5. The method of claim 4wherein the action performed is cancelation of the owner account.
 6. Themethod of claim 3 wherein the notification indicates that the digitalimage is subject to legal issues.
 7. The method of claim 3 furthercomprising: identifying other digital images that have similar metadataas the digital image.
 8. The method of claim 1 wherein receiving anotification occurs via a notify button displayed to the user with thedigital image.
 9. The method of claim 1 wherein the notification is anemail identifying the digital image.
 10. The method of claim 1 whereinthe action performed on the digital image includes forward the digitalimage to a specialist for review.
 11. A non-transitory computer-readablestorage media encoded with a computer executable instruction formonitoring digital images, comprising instructions for: receiving a useridentity from a user; enabling the user to access a digital image whilethe user operates under the user identity; receiving, a notificationassociated with the digital image from the user while the user operatesunder the user identity, wherein the notification indicates that thedigital image is inappropriate; initiating, an investigation of thedigital image based on the notification received from the user; andperforming an action in response to the investigation that affects thedigital image.
 12. The media of claim 11 wherein the action performed isto block the user identify from accessing the digital image.
 13. Themedia of claim 11 wherein the digital image is associated with an owneraccount and the action performed is blocking the owner account.
 14. Themedia of claim 13 wherein the action performed is to block all digitalimages associated with the owner account.
 15. The media of claim 14wherein the action performed is cancelation of the owner account. 16.The media of claim 13 wherein the notification indicates that thedigital image is subject to legal issues.
 17. The media of claim 13further comprising instructions for: identifying other digital imagesthat have similar metadata as the digital image.
 18. The media of claim11 wherein receiving a notification occurs via a notify button displayedto the user with the digital image.
 19. The media of claim 11 whereinthe notification is an email identifying the digital image.
 20. Themedia of claim 11 wherein the action performed on the digital imageincludes forward the digital image to a specialist for review.